Skip to content

Conversation

@dmi3y
Copy link
Contributor

@dmi3y dmi3y commented Apr 16, 2014

re #449

Added ability to pass .csslintrc file path as: csslint --config=<path to .csslintrc> <css to lint>, and as well bit of YUI unit tests to check this functionality.

Notes:

  • This also works with CLI as: csslint --config=<path to .csslintrc> --ignore=<ignores> <css to lint>,
    in this case the ignore from rc file would be overrided by cli, which is current behavior.
  • Rc file could have any valid file name.
  • For unit tests, api stubbing used with vm code execusion for main common.js cli code, also fs was faked as json like file.
  • Look up file traversing to search closest .csslintrc, which was mentioned into config csslintrc path with command line #449, is not part of this PR

dmi3y added 3 commits April 16, 2014 00:40
CSSLint mix helper from utils to mix up cli and rc options
dmi3y added 2 commits April 20, 2014 05:10
CSSLint mix helper from utils to mix up cli and rc options
@joshuaspence
Copy link

+1 for this... is this likely to be merged?

nschonni added a commit that referenced this pull request May 13, 2014
Allow config file path to be passed through the CLI
@nschonni nschonni merged commit f844802 into CSSLint:master May 13, 2014
@joshuaspence
Copy link

Awesome... any chance of a version bump for npm?

@nschonni nschonni added this to the 0.11.0 milestone May 13, 2014
@madskristensen
Copy link

+1 on updating the npm package with this

@JeffHing
Copy link

JeffHing commented Oct 7, 2015

+1 on updating the npm package with this also.

@dmi3y dmi3y deleted the cliconfig branch October 9, 2015 00:40
@XhmikosR XhmikosR modified the milestones: 0.11.0, 1.0.0 Jan 9, 2016
@LeonardoGentile
Copy link

Could you please release this on npm?

@Arcanemagus
Copy link
Contributor

@LeonardoGentile see the latest comments on #514 for the (current) reason this hasn't been released yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants